blocked by #11646

blocked by #12286

can we ignore old migrations and only apply this rule to newer ones? it feels very wrong and error-prone to go back and re-write dozens of old migrations that have been working for a while

@mrsdizzie at this point this are indirect dependencys

for example on v70: the setting.Service.DefaultEnableDependencies value is used.
setting.Service struct as one field (not that one) who is a type decrlared in structs

So my suggestion where: for dependencys: ignores structs and just deny direct imports for structs

Just ignore the previous is better I think. Maybe we need a white list for these files on vet to do that.

@lunny https://gitea.com/gitea/gitea-vet/pulls/9

Codecov Report

Merging #12282 into master will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #12282   +/-   ##
=======================================
  Coverage   43.76%   43.76%           
=======================================
  Files         631      631           
  Lines       69870    69870           
=======================================
+ Hits        30580    30582    +2     
+ Misses      34338    34336    -2     
  Partials     4952     4952           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eb60a5d...1a5b2f4. Read the comment docs.

🚀